TO WHOM IT MAY CONCERN:

 

Dear Sirs;

 

I am interested in applying for a position on the LRDR program’s software development or simulation efforts. I have a broad software and hardware background, including embedded, real-time and radar modelling experience. Also, on several occasions, I have been asked to lead technical efforts.

I’ve worked radar modeling on three programs. On Extended Area Protection System Part-2 (EAPS-2) we modelled from equations and geometries the Technovative interferometric radar, which we were incorporating into our system. Both RF detection and interferometric based position calculation were addressed. 

On Extended Area Protection System Part-1 (EAPS-1),  I implemented radar equations provided by NGES inside the real time HWIL test system. This was necessary due to real time performance requirements and a total system latency of 30 milliseconds (cradle to grave).

During capture efforts, we integrated and I modified a monolithic radar model from a team-member into our simulation suite.  (I adjusted the radar’s scan processing to couple it with threat truth state updates).

I’ve have also recently worked RF, RF propagation, and receiver sensitivity, et.al. I co-developed the EBCS RF Test cell. We use it to stress EBCS’s radio based communication system by injecting RF attenuation under computer control – so called deep and shallow fade. This allows us to induce the type of atmospheric problems reported by soldiers in the Middle East. (We didn’t do rain, though.)  Such injected attenuation is also be used to trigger mesh-style radios to reroute the RF link around the affected area. I mention this because radars are a very special type of radio.

I designed and developed the launch control card on EAPS-2.  This single board computer (Curtis Wright SVME-183) ran VxWorks. My real-time embedded applications were responsible for physically launching the EAPS-2 missile.  Through board support packages, high power supplies squibbed (started) the on board battery and squibbed (fired) the missile motor. Tens of microsecond accuracy and timing were required.   My software also handled pre-launch umbilical updates that gave the missile’s onboard flight controller a simulated target location. This allowed the missile to safely pitch over in the direction of the simulated target (down range, please!). Before sequestration, I had just enough time to work with GE to port our preferred Linux real time os OS ( Red-Hawk ) onto their line of XVR14,15,16 SBC’s, giving us single real-time os across all platforms. This was to replace the C/W SVME-183’s.

My area of expertise in the software design discipline is Pattern development – overall most used is Part Whole and Observer patterns.  My favorite software implementation technology is distributed middleware. I first began using and promoting distributed middleware coincident with publishing of the Object Management Group’s standards (Real time CORBA, then DDS). Specific products include ACE/TAO and then Open-Splice.

Hardware “fun” includes porting interesting code to some of the newer DSP (evaluation cards). My current toy is the TMDSEVM6678L.  Software fun is writing and using antenna design programs like EzNEC.

Yes, I’m a radio amateur, extra license, W4LWS. Packet radio, DSTAR digital radio, and ways to bounce signals off satellites and the moon (;-0 using the 1200 MHZ band.

In terms of computer science tools, I’ve used Java, C++, C, Python, and Perl (from the past … PL/I, Snobol, SmallTalk, and Forth).  Build tools make, gmake, pmake (parallel). Make makers cmake and MPC. Version control, Git, Subversion, ClearCase and ClearQuest, SCCS. Gdb, Ddd.  Glass Fish, Eclipse, VisualStudio.

 

 

Thank you.,

Wayne

 

Lawrence W Sherman

EBCS Citadel Integration Team Lead

Northrop Grumman

301 Voyager Way

Huntsville, Al 35805

256-327-6222

256-881-4940

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Resume:September 18, 2015

 

Lawrence Wayne ShermanSeptember 18, 2015

333 Pawnee Trail

Huntsville, Al 35803

256-327-6222 (d)

256-881-4940 (n)

lawrencewsherman@comcast.net

Position:  Senior software developer or Lead

Languages: Java, C++, C, Python, and Perl (from the past … PL/I, Snobol, SmallTalk, and Forth).  Build tools make, gmake, pmake (parallel). Make makers cmake and MPC. Version control, Git, Subversion, ClearCase and ClearQuest, SCCS. Gdb, Ddd.  Glass Fish, Eclipse, VisualStudio.

 

Professional Experience:

(Radar function or performance workReal-time & embedded work)

2014 – Present Northrop Grumman – Citadel Integration Lead

•         Designed SIL architecture for testing tactical system (software and hardware).

•         Design and development of EBCS (Enterprise Battle Command system) simulation models which represent threat evaluation, battlespace definition, weapon/target assignment and engagement execution.

•         Coded and tested Threat Evaluation model

 

•         Developed RF Test Cell used to simulate harsh RF environments which compromise I.P.  Radio based networks and study the tactical systems responses. Developed math models representing radio signal propagation over terrain with occasional dust storms affecting attenuation to include transmit power, frequency and distance (loss), antenna gain and sensitivity of receiver.

•         Discovered latent flaw in Rajant radio microcode that caused excessive data loss when adverse atmospheric conditions forced a reroute of the I.P. data path

•         Worked w/ ith Rajant to correct in microcode, tested tactical performance.

 

•         Lead tiger team integrating Information Assurance technology into dismount soldier’s command & control tablet (Samsung Knox Provisioning)

 

2013 - 2014 Northrop Grumman Tactical Missiles Simulation Lead/Developer

•         Responsible for developing a variable fidelity simulation tool kit to support design and capture efforts, including innovate solid state missile thrust technology

•         Worked synchronizing the radar’s scan processing with truth model state updates as well as conversion from real-time to faster than real-time mode

•         Supported modelling several existing tactical missiles used to defend against Rocket Artillery Mortar (RAM) and Unmanned Air Vehicle (UAV) threats

•         Integrated models of flight characteristics from missile maker Matra Defense of France and Bae Dynamics (MBDA) into our performance simulation

•         Developed hardware emulator for chin camera/laser pod on NG’s Hunter Unmanned Aerial Vehicle at Redstone Arsenal’s Software Engineering Directorate, & Sierra Vista. With the emulator enabled, pilots were able to safely train “firing” the laser designators.  The emulator was designed to act like the real pod, including gear lash behavior, tactical communication with aircraft’s flight computer (rs-485), slewing pod in azimuth & elevation resulting in a full 3d display of the 6 degrees of freedom aircraft model. We included animation of the pod reacting to pilot command, with representative laser beams being fired and camera field of view piped into shelter into pilot shelter.

 

2012 – 2013 Northrop Grumman Extended Area Protection System (EAPS) Part-2 Hardware in the Loop Lead

•                                  Developed new airframe model when new motor and warhead were added for improved lethality.

•                                  Responsible for all modifications to ID simulation (IDSIM) in support of program’s new interferometric radar.  EAPS provides protection from Rocket, Artillery and Mortar threats (RAM). As the interceptor had no on board seeker (significant cost benefit),

Guidance came solely from organic radar. Interferometric radars provide the necessary position accuracy of both threat and interceptor. The selected radar was made by Technovative Applications. Under nondisclosure, NGC was given pertinent parameters that allowed us to represent the radar’s performance. (See included brief on modelling interferometry). Performed integration and testing

•                                  Supported simulation as analysis tool for chief engineer to verify system design

•                                  Designed and prototyped launch facility in support of test range operations.

Included “two key launch” enable in the block house, redundant fiber connection to missile launch pad (dog house) and actual launch controller software on VxWorks / SVME183 single board computer. I programmed his card to handle actual squibbing (“firing”) of battery and motor, based on launch command from block house. Immediately before launch, my software generated the umbilical update which contained the most recent simulated position of the threat, so pitch over could correctly occur. I also developed a network of embedded (PIC32) microcontrollers used as the launcher safety layer, a totally independent & redundant “truth” reporting system, all networked using Ethernet and I.P.

 

2009 – 2012 Northrop Grumman Extended Area Protection System (EAPS) HardWare in the Loop (HWIL) Lead

•                                  Acted as HWIL lead for the EAPS program.  Designed / Developed EAPS (Extended Area Protection System) HWIL (HardWare in the Loop) system.  Implemented real-time software which drove the EAPS missile during test scenarios, including radio based uplink messages.

Implemented control of the “Rate Table” at Redstone Arsenal (McMorrow Labs) which emulated flight dynamics.  A rate table is a test fixture which moves the missile under test in all three axis (roll, pitch, and yaw) under software control. This makes the avionics section of the missile (containing the onboard inertial measurement unit) think it is in flight (except of course without linear acceleration). This allows for a very accurate test of the missile guidance capabilities while still in the lab. I used Concurrent IHAWK systems running Red-Hawk real-time os. Responsible for organizing and performing numerous HWIL entries at AMRDEC test labs.

•         Performed all updates & fixes to the NGES supplied radar model. This included rewriting is so it would run real time (a requirement), making fixes like being able to turn on/ off stochastic modelling, when we needed reproducible answers. I also had to modify the radar’s use of time, since we had a 32 msec latency requirement from radar to missile.

2006 – 2009 Northrop Grumman Kinetic Energy Interceptor (KEI) Modelling & Simulation Engineer

•                                  Developed models on KEISIM, the 6dof simulation package used to evaluate interceptor and fire control design under the EARLY boost conops

•                                  Re-implemented simulation infrastructure and models between  FORTRAN,  Java and  C++  based on performance requirements

•         Developed a distributed simulation middleware to allow models to run outside of the single monolithic executable

2002 – 2006 Teledyne Missile Defense System Exerciser

•                                  Wrote improved  “threat tape” based threat model using Part Whole pattern

•         Wrote tools to quickly dump large data set into Oracle database

•         Developed an open source simulation framework and ported several MDSE models into the framework.

•         Developed digital audio recording & search tool used during exercises and tests

•                      Developed tool to decode VMF tactical messages and display them graphically (heavily used QT toolkit)

1997 – 2002 Teledyne Extended Air Defense SIMulation

•         Developed various models including launchers and fusion posts

•         Implemented a physics based model of an antenna emitter used to publish emitter status to other simulations

•         Worked on simulation performance enhancement

•                      Integrated EADSIM tracking filters with outside tools such as the NAVY exercise servers and AEGIS Anti Air Warfare Officer’s Console

1993 – 1997 Teledyne Advanced Field Artillery System

•         Developed Ada software used in drive by wire control system

•         Acted as SIL engineer, in which I integrated all the Ada code it into the SIL test bed

1989 – 1993 Sun Microsystems

•          Ada development product specialist

1977 – 1989 Intergraph Corp.

•         Software Engineer developing tools for CAD/CAM and computer aided engineering (CAE) products including schematic capture, design rules checking, automatic placement and routing of boards. Also integrated digital logic simulator and analog circuit simulator into schematic capture package.

 

Education:

•         B.S. Physics / Chemistry – Birmingham Southern College 1972-1976

•         Graduate work / Masters UAH Computer Science 1978 – 1982[AG1]

Clearance:

•         Active SECRET

Hobbies:

•         Radio Amateur Extra Class License – W4LWS

•         Building electronics / programming PIC systems

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

MEMO                                                                     

 

Subject: My Interferometric Radar Notes

From:     Wayne Sherman

To:    File

Interferometric radars use multiple individual antennas, carefully arranged in a pattern across the transceiver front face. These receive the reflected radar energy originally sent by the transmitting antenna. See left, the center module is the transmitter, the outer three, receivers. Their spatial relationship is carefully measured. 

Next, see above, the difference between a traditional and an interferometric type radar. Notice especially that two antenna (A1 and A2) are receiving reflected radar energy, and that position of A1 and A2 are very accurately known. This allows us to measure the phase difference of the returning wave front across the entire array (or an encoded signal yielding timing). Again, knowing the transmitter/receiver geometry very accurately, frequency and speed of propagation, we can calculate this geometry, yielding the desired position data.

We organized our work into two steps.  First was to represent the more traditional detection process.  Can the receiver detect the transmission/reflection (radar range equation) ?The equations express transmitted power, radar cross section, attenuation and noise sources, antenna gain and then radar receiver sensitivity.  Each receiver antenna must be processed in exactly this way.  Each of these individual antenna can be processed in parallel.  If a detection occurs, we moved to the second part. Here we were concerned with measuring the position the target, from each antenna. The two diagrams above show how the antennas must solve the geometry. However, for the purpose of modelling, we took a slightly direct approach. The true position of the object being tracked (“truth”) and of that of the radar are well known. This allows us to calculate the targets true position relative to the radar.  Using angular accuracy figures from Technovative, an error box about the targets “true” location was calculated.  A random draw was made and applied to the position error, which is then added to the truth position.  (The subject of co-variance is beyond our scope, but is allied.)  We advance time and the targets threat position moved. Each antenna is re-run at the new time step, producing the next positions. The “history” of these points was then feed into our tracking algorithm. This “track file” is shared with all the other simulants that want to know the threat location.

 

 

Wayne Sherman

333 Pawnee Trail

Huntsville, Al

 

Wayne.sherman@ngc.com

 

 

Acronyms:

 

------------    -------------  ------------

 

L	1 to 2 GHz	Long wave
S	2 to 4 GHz	Short wave
C	4 to 8 GHz	Compromise between S and X
X	8 to 12 GHz	Used in WW II for fire control, X for cross (as in crosshair)
Ku	12 to 18 GHz	Kurz-under
K	18 to 27 GHz	German Kurz (short)
Ka	27 to 40 GHz	Kurz-above

 

 

 

[AG1]Did you complete your master’s?  It reads as though you did not, so if you did , let me know.